Create SECURITY.md for security policy and reporting #2052
Conversation
Added a security policy document outlining supported versions and vulnerability reporting.
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Summary of ChangesHello @PichaiTK, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces a formal security policy for the project. Its purpose is to clearly communicate which project versions receive security support and to establish a standardized process for users to report security vulnerabilities, thereby enhancing the project's overall security posture and transparency. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds a SECURITY.md file, which is an important step for defining the project's security policy. However, the current file is a template with placeholder content. It needs to be updated with specific information for the 'Now in Android' project. I've added comments with suggestions for completing the 'Supported Versions' and 'Reporting a Vulnerability' sections. Filling out this information is crucial to provide clear and actionable security guidance to your users and contributors.
| Use this section to tell people about which versions of your project are | ||
| currently being supported with security updates. | ||
|
|
||
| | Version | Supported | | ||
| | ------- | ------------------ | | ||
| | 5.1.x | :white_check_mark: | | ||
| | 5.0.x | :x: | | ||
| | 4.0.x | :white_check_mark: | | ||
| | < 4.0 | :x: | |
There was a problem hiding this comment.
This 'Supported Versions' section appears to be a template. Please replace the placeholder text and the example versions in the table with the actual supported versions of the 'Now in Android' app and their current security support status.
| Use this section to tell people how to report a vulnerability. | ||
|
|
||
| Tell them where to go, how often they can expect to get an update on a | ||
| reported vulnerability, what to expect if the vulnerability is accepted or | ||
| declined, etc. |
There was a problem hiding this comment.
This 'Reporting a Vulnerability' section is a template and lacks specific instructions. This is a critical part of the security policy. Please provide a clear process for reporters. A good practice is to enable and link to GitHub's private vulnerability reporting feature, and set expectations for response times.
| Use this section to tell people how to report a vulnerability. | |
| Tell them where to go, how often they can expect to get an update on a | |
| reported vulnerability, what to expect if the vulnerability is accepted or | |
| declined, etc. | |
| Please report security vulnerabilities by using the [GitHub private vulnerability reporting feature](https://github.com/android/nowinandroid/security/advisories/new). | |
| We aim to acknowledge receipt of the report within 48 hours and provide a more detailed response within 72 hours with the next steps. |
1 participant
Added a security policy document outlining supported versions and vulnerability reporting.
DO NOT CREATE A PULL REQUEST WITHOUT READING THESE INSTRUCTIONS
Instructions
Thanks for submitting a pull request. To accept your pull request we need you do a few things:
If this is your first pull request
Ensure tests pass and code is formatted correctly
DemoDebugvariant by running./gradlew testDemoDebug./gradlew --init-script gradle/init.gradle.kts spotlessApplyAdd a description
We need to know what you've done and why you've done it. Include a summary of what your pull request contains, and why you have made these changes. Include links to any relevant issues which it fixes.
Here's an example.
NOW DELETE THIS LINE AND EVERYTHING ABOVE IT
What I have done and why
<add your PR description here>